Epoch-based mud logging

ABSTRACT

In one embodiment, a MUD logger receives a notification from another MUD logger maintaining another MUD log for a volume, the notification indicating one or more modifications to be made to a MUD log maintained by the MUD logger receiving the notification, wherein the MUD log includes information for one or more epochs, wherein the information for each of the epochs indicates a set of one or more regions of the volume that have been modified during the corresponding epoch. The MUD logger updates the MUD log associated with the volume, wherein updating the MUD log is performed in response to the notification.

RELATED APPLICATIONS

This application is a continuation application and claims priority ofU.S. patent application Ser. No. 11/494,036, Attorney Docket No.CISCP492/897857, entitled, “EPOCH-BASED MUD LOGGING,” by Sharma et al,filed on Jul. 26, 2006, which is incorporated by reference for allpurposes.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates to network technology. More particularly,the present invention relates to methods and apparatus for implementingMUD logging in a system implementing virtualization of storage within astorage area network.

2. Description of the Related Art

In recent years, the capacity of storage devices has not increased asfast as the demand for storage. Therefore a given server or other hostmust access multiple, physically distinct storage nodes (typicallydisks). In order to solve these storage limitations, the storage areanetwork (SAN) was developed. Generally, a storage area network is ahigh-speed special-purpose network that interconnects different datastorage devices and associated data hosts on behalf of a larger networkof users. However, although a SAN enables a storage device to beconfigured for use by various network devices and/or entities within anetwork, data storage needs are often dynamic rather than static.

The concept of virtual memory has traditionally been used to enablephysical memory to be virtualized through the translation betweenphysical addresses in physical memory and virtual addresses in virtualmemory. Recently, the concept of “virtualization” has been implementedin storage area networks through various mechanisms. Virtualizationinterconverts physical storage and virtual storage on a storage network.The hosts (initiators) see virtual disks as targets. The virtual disksrepresent available physical storage in a defined but somewhat flexiblemanner. Virtualization provides hosts with a representation of availablephysical storage that is not constrained by certain physicalarrangements/allocation of the storage.

Virtualization in the storage array is one of the most common storagevirtualization solutions in use today. Through this approach, virtualvolumes are created over the storage space of a specific storagesubsystem (e.g., disk array). Creating virtual volumes at the storagesubsystem level provides host independence, since virtualization of thestorage pool is invisible to the hosts. In addition, virtualization atthe storage system level enables optimization of memory access andtherefore high performance. However, such a virtualization schemetypically will allow a uniform management structure only for ahomogenous storage environment and even then only with limitedflexibility. Further, since virtualization is performed at the storagesubsystem level, the physical-virtual limitations set at the storagesubsystem level are imposed on all hosts in the storage area network.Moreover, each storage subsystem (or disk array) is managedindependently. Virtualization at the storage level therefore rarelyallows a virtual volume to span over multiple storage subsystems (e.g.,disk arrays), thus limiting the scalability of the storage-basedapproach.

When virtualization is implemented on each host, it is possible to spanmultiple storage subsystems (e.g., disk arrays). A host-based approachhas an additional advantage, in that a limitation on one host does notimpact the operation of other hosts in a storage area network. However,virtualization at the host-level requires the existence of a softwarelayer running on each host (e.g., server) that implements thevirtualization function. Running this software therefore impacts theperformance of the hosts running this software. Another key difficultywith this method is that it assumes a prior partitioning of theavailable storage to the various hosts. Since such partitioning issupported at the host-level and the virtualization function of each hostis performed independently of the other hosts in the storage areanetwork, it is difficult to coordinate storage access across the hosts.The host-based approach therefore fails to provide an adequate level ofsecurity. Due to this security limitation, it is difficult to implementa variety of redundancy schemes such as RAID which require the “locking”of memory during read and write operations. In addition, when mirroringis performed, the host must replicate the data multiple times,increasing its input-output and CPU load, and increasing the trafficover the SAN.

Virtualization in a storage area network appliance placed between thehosts and the storage solves some of the difficulties of the host-basedand storage-based approaches. The storage appliance globally manages themapping and allocation of physical storage to virtual volumes.Typically, the storage appliance manages a central table that providesthe current mapping of physical to virtual. Thus, the storageappliance-based approach enables the virtual volumes to be implementedindependently from both the hosts and the storage subsystems on thestorage area network, thereby providing a higher level of security.Moreover, this approach supports virtualization across multiple storagesubsystems. The key drawback of many implementations of thisarchitecture is that every input/output (I/O) of every host must be sentthrough the storage area network appliance, causing significantperformance degradation and a storage area network bottleneck. This isparticularly disadvantageous in systems supporting a redundancy schemesuch as RAID, since data must be mirrored across multiple disks. Inanother storage appliance-based approach, the appliance makes sure thatall hosts receive the current version of the table. Thus, in order toenable the hosts to receive the table from the appliance, a softwareshim from the appliance to the hosts is required, adding to thecomplexity of the system. Moreover, since the software layer isimplemented on the host, many of the disadvantages of the host-basedapproach are also present.

Patent application Ser. No. 10/056,238, Attorney Docket No. ANDIP003,entitled “Methods and Apparatus for Implementing Virtualization ofStorage in a Storage Area Network,” by Edsall et al, filed on Jan. 23,2002, discloses a system in which network-based virtualization issupported. In other words, virtualization is supported in the network,rather than at the hosts or storage devices. In this system,virtualization is supported by one or more network devices placed in adata path between the hosts and the storage devices. More particularly,virtualization may be implemented on a per-port basis via “intelligentports.”

In a system implementing storage virtualization, virtual volumes aretypically created over the storage space of a specific storage subsystem(e.g., disk array). More particularly, data is often mirrored acrossmultiple storage devices (e.g., disks) such that the same data is storedacross each of the storage devices. Storage devices storing the samedata are typically referred to as mirrors. Through the use of mirroring,redundancy may be accomplished. As a result, the data that is stored ineach of the mirrors will remain accessible to hosts in the event of aproblem with one of the mirrors.

In the event that one of the storage devices goes offline, it isdesirable to bring the storage device up to date when the storage deviceis brought back online. This process typically involves copying all ofthe data from one of the mirrors to the temporarily detached mirror.Unfortunately, this process could take hours. As a result, the host willtypically detect a disruption to data access.

In order to alleviate the need to copy all of the data from a mirrorduring the recovery process, a Modified User Data (MUD) log is oftenused. A MUD log is typically maintained on a per-mirror basis. In otherwords, a separate log is maintained for each storage device. While thisMUD logging process is effective for systems implementing disk-basedvirtualization, this type of process is ineffective in a systemimplementing network-based virtualization.

In a system in which a volume is exported by multiple network devices ormultiple ports that may implemented on different network devices, thestandard MUD logging process is ineffective. More particularly, writecommands may be sent via different intelligent ports, as well asdifferent network devices. Although the data in a volume could bemodified through several intelligent ports or network devices, theintelligent ports or network devices cannot coordinate amongstthemselves to maintain a consistent MUD log for the volume. As a result,managing and maintaining MUD logs becomes a difficult process.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example system architecture inwhich various embodiments may be implemented.

FIG. 2 is an example timeline illustrating a plurality of epochs.

FIG. 3 is a diagram illustrating a MUD log that may be maintained inaccordance with one embodiment.

FIG. 4 is a diagram illustrating an example bit map that may beassociated with an epoch in accordance with one embodiment.

FIG. 5 is a process flow diagram illustrating a method of implementingMUD logging by a master MUD logger in accordance with one embodiment.

FIGS. 6A-B are process flow diagrams illustrating methods ofimplementing MUD logging by a non-master MUD logger in accordance withone embodiment.

FIG. 7A is an example diagram illustrating the information for twodifferent epochs.

FIG. 7B is an example diagram illustrating a mechanism for merging twoor more epochs.

FIG. 8A is a block diagram illustrating an example virtualization switchin which various embodiments may be implemented.

FIG. 8B is a block diagram illustrating an example standard switch inwhich various embodiments may be implemented.

DESCRIPTION OF EXAMPLE EMBODIMENTS

In the following description, numerous specific details are set forth inorder to provide a thorough understanding of the disclosed embodiments.It will be obvious, however, to one skilled in the art, that thedisclosed embodiments may be practiced without some or all of thesespecific details. In other instances, well-known process steps have notbeen described in detail in order not to unnecessarily obscure thedisclosed embodiments.

Overview

In one embodiment, a MUD logger receives a notification from another MUDlogger maintaining another MUD log for a volume, the notificationindicating one or more modifications to be made to a MUD log maintainedby the MUD logger receiving the notification, wherein the MUD logincludes information for one or more epochs, wherein the information foreach of the epochs indicates a set of one or more regions of the volumethat have been modified during the corresponding epoch. The MUD loggerupdates the MUD log associated with the volume, wherein updating the MUDlog is performed in response to the notification.

Specific Example Embodiments

The disclosed embodiments may support MUD logging in a systemimplementing virtualization. More particularly, the embodimentsdescribed herein may be implemented in a system implementingnetwork-based virtualization. In a system implementing network-basedvirtualization, virtualization may be implemented across multiple portsand/or network devices such as switches or routers that are in the pathbetween hosts and storage devices. As a result, write commands addressedto a volume may be intercepted by different network devices (e.g.,switches, routers, etc.) and/or ports.

In accordance with one aspect, MUD logging for a volume is performed bytwo or more MUD loggers. Each of the MUD loggers therefore maintains aseparate MUD log. Information pertinent to the MUD log may also betransmitted between or among the MUD loggers, enabling the MUD loggersto update their MUD logs. Since communication is supported among the MUDloggers, each MUD logger may maintain an updated MUD log.

In accordance with one embodiment, the MUD loggers include a master MUDlogger and one or more secondary MUD loggers. The master MUD logger isresponsible for notifying one or more of the secondary MUD loggers whena modification is to be made to the MUD log maintained by the secondaryMUD loggers (e.g., as a result of a write command addressed to thevolume). In addition, each secondary MUD logger may communicate with themaster MUD logger regarding modifications to the MUD log initiated bythe secondary MUD logger (e.g., as a result of a write commandintercepted by the secondary MUD logger), enabling the master MUD loggerto notify any remaining secondary MUD loggers that export the volume.

In accordance with another aspect, communication among MUD loggers isachieved by sending a notification from one MUD logger to one or moreother MUD loggers. This notification may indicate the changes to be madeto the MUD log, or may notify the other MUD logger(s) of a write thathas been performed (or a write command that has been received),resulting in one or more modifications to one or more regions of avolume. In accordance with one embodiment, a notification may be sent bya master MUD logger to one or more secondary MUD loggers or,alternatively, a notification may be sent by a secondary MUD logger tothe master MUD logger. An acknowledgement of such a notification may besent in response to the notification.

In accordance with yet another aspect, each MUD log includes informationfor one or more epochs, where the information for each of the epochsindicates a set of one or more regions that have been modified duringthe corresponding epoch. The information for a particular epoch may beimplemented in a variety of ways. In accordance with one embodiment, theinformation is stored in a bit map including a plurality of bits, whereeach bit corresponds to a different region of the volume. Each bit ofthe bit map therefore indicates whether the corresponding region hasbeen modified during the corresponding epoch.

In accordance with another embodiment, a notification is sent only wherethe corresponding region of the volume has not yet been modified duringthe epoch. In other embodiments, a notification is sent regardless ofwhether the region of the volume has already been modified during theepoch. In these instances, the MUD logger receiving the notification maydetermine whether it needs to modify its local MUD log.

In accordance with one aspect, a MUD logger maintains a MUD logassociated the volume, wherein the MUD log includes information for oneor more epochs, where the information for each of the epochs indicates aset of one or more regions that have been modified during thecorresponding epoch. The MUD logger may also send a notification toanother MUD logger. The notification may indicate one or moremodifications to be made to a MUD log maintained by the MUD loggerreceiving the notification. The notification may also indicate one ormore regions of the volume that have been modified during the currentepoch (e.g., which may or may not warrant modification to a MUD log,depending upon previous modifications to the volume and MUD log duringthe epoch).

In accordance with another aspect, a MUD logger updates its MUD logassociated with a volume that it exports, as appropriate. Updating mayinclude a variety of operations, such as merging two or more epochs,deleting (e.g., clearing) an epoch, and generating a new epoch.

In accordance with another embodiment, a particular event may define thestart of a new epoch. Such events may include, for example, theattachment of a mirror, the reattachment of a mirror, or the detachmentof a mirror. By defining events in this manner, it is possible to tracka period of time during which a mirror is non-functional. In thismanner, modifications made to a volume during a particular epoch may betracked in an efficient manner in order to update the mirror when it isreattached. Accordingly, mirrors may be efficiently updated withoutrequiring unnecessary data to be restored.

In accordance with one aspect, two or more MUD loggers export a volume.Each MUD logger may be implemented in a variety of ways. For instance,each MUD logger may be implemented at a separate network device. Asanother example, each MUD logger may be implemented via a separate portof a network device such as a switch or router.

In accordance with one embodiment, each of the MUD loggers isimplemented at a different one of the ports that exports the volume.Since a volume may be exported by multiple ports, each of the portsmaintains a separate MUD log. In order to enable the informationmaintained at each port to be updated and remain current, communicationbetween or among the ports may be supported, as will be described infurther detail below.

The ports that export a particular volume may be implemented in one ormore network devices within the network. In accordance with oneembodiment, the ports may be intelligent ports (i.e., I-ports)implemented in a manner such as that disclosed in patent applicationSer. No. 10/056,238, Attorney Docket No. ANDIP003, entitled “Methods andApparatus for Implementing Virtualization of Storage in a Storage AreaNetwork,” by Edsall et al, filed on Jan. 23, 2002. An I-port may beimplemented as a master port, which may send commands or information toother I-ports. In contrast, an I-port that is not a master port maycontact the master port for a variety of purposes, but cannot contactthe other I-ports. In a Fibre Channel network, the master I-port for aparticular volume may maintain the identity of the other I-ports thatalso export the volume in the form of a World Wide Name (WWN) and/orFibre Channel Identifier (FCID). Similarly, the other I-ports thatexport the volume may maintain the identity of the master I-port in theform of a WWN and/or FCID. In other embodiments, it is contemplated thatthe system does not include a master I-port, and therefore the I-portsmaintain the identity of the other I-ports that export the volume towhich they send notifications.

In accordance with one embodiment, a master port functions as a masterport for purposes of MUD logging. In addition, the master port may alsofunction as a master port for purposes of implementing virtualizationfunctionality. More particularly, a master port may be implemented in amanner such as that disclosed in patent application Ser. No. 10/056,238,Attorney Docket No. ANDIP003, entitled “Methods and Apparatus forImplementing Virtualization of Storage in a Storage Area Network,” byEdsall et al, filed on Jan. 23, 2002.

In accordance with one embodiment, a storage area network may beimplemented with virtualization switches adapted for implementingvirtualization functionality, as well as with standard switches. FIG. 1is a block diagram illustrating an example system architecture in whichvarious embodiments may be implemented. In this example, twovirtualization switches 102 and 104 are implemented to supporttransmission of frames within the storage area network. Eachvirtualization switch may include one or more “intelligent” ports aswell as one or more standard ports. More specifically, thevirtualization switches 102 and 104 in this example each have anintelligent port 106 and 108, respectively. In addition, each of thevirtualization switches 102 and 104 has multiple standard ports 110,112, 114, 116 and 118, 120, 122, 124, respectively.

In order to support the virtual-physical mapping and accessibility ofmemory by multiple applications and/or hosts, it is desirable tocoordinate memory accesses between the virtualization switches 102 and104. Communication between the switches 102 and 104 may be accomplishedby an inter-switch link 126 between two switches. As shown, theinter-switch link 126 may be between two standard ports. In other words,synchronization of memory accesses by two switches merely requirescommunication between the switches. This communication may be performedvia intelligent virtualization ports, but need not be performed via avirtualization port or between two virtualization ports.

Virtualization of storage is performed for a variety of reasons, such asmirroring. For example, consider four physical Logical Units (LUNs)LUNs, PLUN1 128, PLUN2 130, PLUN3 132, and PLUN4 134. It is oftendesirable to group two physical LUNs for the purpose of redundancy.Thus, as shown, two physical LUNs, PLUN1 128 and PLUN2 130 arerepresented by a single virtual LUN, VLUN1 136. When data is mirrored,the data is mirrored (e.g., stored) in multiple physical LUNs to enablethe data to be retrieved upon failure of one of the physical LUNs.

Various problems may occur when data is written to or read from one of aset of “mirrors.” For instance, multiple applications running on thesame or different hosts, may simultaneously access the same data ormemory location (e.g., disk location or disk block), shown as links 138,140. Similarly, commands such as read or write commands sent from twodifferent hosts, shown at 138, 140 and 142, 143 may be sent in the sametime frame. Each host may have corresponding Host Bus Adapters (HBA) asshown. Ideally, the data that is accessed or stored by the applicationsor hosts should leave the mirrors intact. More particularly, even aftera write operation to one of the mirrors, the data stored in all of themirrors should remain consistent. In other words, the mirrors shouldcontinue to serve as redundant physical LUNs for the other mirrors inthe event that one of the mirrors should fail.

In conventional systems in which mirroring is enabled, a relativelysimultaneous access by two different sources often results in aninherent race condition. For instance, consider the situation when twodifferent clients send a write command to the same virtual LUN. Asshown, application 1 144 running on Host 1 124 sends a write commandwith the data “A,” while application 2 146 running on Host 2 126 sends awrite command with the data “B.” If the first application 144 sends data“A” to VLUN1 136 first, the data “A” may be written, for example, toPLUN1 128. However, before it can be mirrored to PLUN2 130, the secondapplication 146 may send data “B.” Data “B” may be written to PLUN2 130prior to being mirrored to PLUN1 128. Data “A” is then mirrored to PLUN2130. Similarly, data “B” is mirrored to PLUN1 128. Thus, as shown, thelast write operation controls the data to be stored in a particularphysical LUN. In this example, upon completion of both mirroroperations, PLUN1 128 stores data “B” while PLUN2 130 stores data “A.”Thus, the two physical LUNs no longer mirror one another, resulting inambiguous data.

In order to solve the inherent race condition present in conventionalsystems, the virtualization ports communicate with one another, asdescribed above, via an inter-switch link such as 126. In other words,the ports synchronize their access of virtual LUNs with one another.This is accomplished, in one embodiment, through the establishment of asingle master virtualization port that is known to the othervirtualization ports as the master port. The identity of the master portmay be established through a variety of mechanisms. As one example, themaster port may send out a multicast message to the other virtualizationports indicating that it is the master virtualization port. As anotherexample, the virtualization ports may be initialized with the identityof the master port. In addition, in the event of failure of the mastervirtualization port, it may be desirable to enable one of the slavevirtualization ports to substitute as a master port.

The master virtualization port may solve the problem caused due to theinherent race condition in a variety of ways. One solution is a lockmechanism. An alternative approach is to redirect the SCSI command tothe master virtualization port, which will be in charge of performingthe virtual to physical mapping as well as the appropriate interlocking.The slave port may then learn the mapping from the master port as wellas handle the data.

Prior to accessing a virtual LUN, a slave virtualization port initiatesa conversation with the master virtualization port to request permissionto access the virtual LUN. This is accomplished through a lockingmechanism that locks access to the virtual LUN until the lock isreleased. For instance, the slave virtualization port (e.g., port 106)may request the grant of a lock from the master virtualization port(e.g., port 108). The master virtualization port then informs the slavevirtualization port when the lock is granted. When the lock is granted,access to the corresponding physical storage locations is “locked” untilthe lock is released. In other words, the holder of the lock hasexclusive read and/or write access to the data stored in those physicallocations. In this example, data “A” is then stored in both physicalLUN1 128 and physical LUN2 130. When the slave virtualization port 106receives a STATUS OK message indicating that the write operation to thevirtual LUN was successful, the lock may be released. The mastervirtualization port 108 may then obtain a lock to access of the virtualLUN until data “B” is stored in both mirrors of the VLUN1 136. In thismanner, virtualization ports synchronize access to virtual LUNs toensure integrity of the data stored in the underlying physical storagemediums.

In accordance with one embodiment, slave and master virtualization portsmay be configured or adapted for performing MUD logging operations suchas those described herein. More particularly, select MUD logging portsmay each maintain a respective separate MUD log, as well as communicatewith one another regarding MUD logging processes, as will be describedin further detail below.

In accordance with one aspect, MUD logging is performed for one or moreepochs. An epoch may be defined as a period of time. The beginning ofthe epoch may be marked by a particular event. Similarly, the end of anepoch may also be marked by a specific event. In this manner, an epochmay be defined by one or more events. An event may be, for example, theattachment of a mirror (or disk), detachment (or failure) of a mirror,or reattachment of a mirror. Thus, each epoch may have one or moreevents associated therewith.

FIG. 2 is an example timeline illustrating a plurality of epochs. Asshown in FIG. 2, Epoch B 202 begins at Event #1 204 and ends at Event #2206. Epoch C 208 begins at Event #2 206 and continues up until thepresent time 210. For instance, Event #1 204 may be defined by thedetachment of a mirror, while Event #2 206 may be defined by thereattachment of the mirror. Therefore, Epoch B 202 may define the timeduring which the mirror has been detached. As a result, it may bedesirable to obtain the MUD logging information associated with Epoch Bfrom one of the MUD loggers in order to determine which segments of datahave been modified during this period of time. These segments of datamay then be copied to the newly reattached mirror from another one ofthe mirrors. It is important to note that it is unnecessary to copy dataother than that for the segments of data that have been modified duringthis particular epoch.

In accordance with one embodiment, the MUD logs maintained by each MUDlogger (e.g., port) are epoch-based. FIG. 3 is a diagram illustrating aMUD log that may be maintained by a MUD logger in accordance with oneembodiment. As shown in FIG. 3, a MUD log 302 may be maintained for oneor more volumes. The MUD log 302 may be implemented via anobject-oriented data structure, linked list and/or other suitable datastructure.

In this example, the MUD log 302 is maintained for a volume, Volume A.The MUD log includes information for one or more epochs. In thisexample, the MUD log includes information for a plurality of epochs,Epoch 1, Epoch 2, Epoch 3 . . . . Epoch N. The information for each ofthe epochs indicates a set of one or more regions of the volume thathave been modified during the corresponding epoch.

The information indicating those regions of the volume that have beenmodified may be implemented in a variety of ways. For instance, theregions that have been modified may be identified in a list.Alternatively, regions that have not been modified may be identified ina list. In accordance with one embodiment, the set of regions of avolume that have been modified during a particular epoch may beimplemented via a number of bits or bytes. For instance, a bit mapincluding a bit for each region of the volume of data may be used toidentify the regions that have been modified during a particular epoch.

FIG. 4 is a diagram illustrating an example bit map that may beassociated with an epoch in accordance with one embodiment. In thisexample, the bit map includes 36 bits, each bit representing arespective region of a volume that has, for purposes of this example, 36regions. Each bit indicates whether the corresponding region has beenmodified during the corresponding epoch. More particularly, inaccordance with one embodiment, when the bit is set to 1, the region hasbeen modified during the corresponding epoch. When the bit is set to 0,the region has not been modified during the corresponding epoch.

In accordance with another aspect, MUD logging is performed by two ormore network devices (or ports). Through enabling these networkdevices/ports to communicate with one another, redundant MUD logs may bemaintained. In this manner, redundancy may be accomplished, enablingmirrors to be efficiently restored in the event of a failure.

In accordance with one embodiment, communication may be achieved via aprimary (i.e., master) MUD logger and one or more other secondary MUDloggers. The primary MUD logger not only maintains its own MUD log forthe volume, but is also responsible for notifying one or more othersecondary MUD loggers when a modification is to be made to the MUD logmaintained by the secondary MUD loggers. Stated another way, it isdesirable to notify the secondary MUD loggers when modifications havebeen made to one or more regions of the volume (and therefore the MUDlog of the primary MUD logger). More particularly, the primary MUDlogger may be a master intelligent port as set forth in patentapplication Ser. No. 10/056,238, Attorney Docket No. ANDIP003, entitled“Methods and Apparatus for Implementing Virtualization of Storage in aStorage Area Network,” by Edsall et al, filed on Jan. 23, 2002, whilethe other MUD logger(s) may be intelligent ports as set forth in patentapplication Ser. No. 10/056,238, Attorney Docket No. ANDIP003, entitled“Methods and Apparatus for Implementing Virtualization of Storage in aStorage Area Network,” by Edsall et al, filed on Jan. 23, 2002.

In the following description, reference to a single master MUD logger ismade. However, it is important to note that multiple master MUD loggersmay be desirable. For instance, a different master MUD logger may beassociated with each volume. More particularly, one or more MUD loggers(e.g., master MUD loggers) may be associated with each volume. This maybe accomplished by a separate network device responsible for assigningvolumes to MUD loggers (or vice versa). As another example, it may bedesirable to implement redundancy in the event that a master MUD loggerfails.

FIG. 5 is a process flow diagram illustrating a method of implementingMUD logging by a master MUD logger in accordance with one embodiment.The master MUD logger may initiate the change in a MUD log for a varietyof reasons. One reason that a change to a MUD log may be made is amodification to one or more regions of the volume of data. Moreparticularly, when a write command is sent to the volume, the writecommand may be intercepted by the master MUD logger or another MUDlogger. Therefore, the master MUD logger may receive the write commandor receive a notification of the receipt of a write command directed tothe volume by another MUD logger at 502.

Another reason for modifying a MUD log is the initiation of a new epoch(or end of a prior epoch). More particularly, the master MUD logger maydetect or receive a notification of an event indicating the start of anew epoch at 504. For instance, the master MUD logger may be notifiedthat a particular mirror has failed or been detached from the network.

For a variety of reasons, the master MUD logger may internally initiatea particular modification to the MUD log at 506. This may be desirable,for instance, in order to consolidate information or in response to thedetection of a particular event such as an event initiating the start ofa new epoch. Consolidation may be accomplished, for example, by mergingtwo or more consecutive epochs. It may also be desirable to clear ordelete an epoch, such as where older epochs are deleted and/or archivedto another storage medium or data structure.

Where a new epoch is initiated (or ended), the master MUD logger maymodify its MUD log accordingly. This may be accomplished by generating anew data structure for the new epoch. In addition, it may be desirableto initialize the values in the new epoch data structure by “clearing”the epoch.

Moreover, where the master MUD logger merges two or more consecutiveepochs, the data in the separate data structures may be “merged” andstored in a single data structure, as will be described in furtherdetail below. The epoch data structures that are no longer in use maythen be deleted or cleared.

In circumstances such as those presented in 502-506, the master MUDlogger updates its MUD log at 508, as appropriate. More particularly,where the master MUD logger has received a write command or beennotified of a write command addressed to the volume, the master MUDlogger may update its MUD log to indicate that a particular region orregions have been modified during the epoch. This modification may bemade automatically, or may be made only when the region(s) have notalready been modified during the epoch. In accordance with oneembodiment, the master MUD logger maintains a MUD log only for the mostrecent (i.e., current) epoch. In other words, when a new epoch isgenerated, the prior epoch is deleted or moved to a different location(e.g., bytemap).

The master MUD logger may update its MUD log via a variety ofoperations. These operations include, for example, initiating a newepoch and merging two or more consecutive epochs. Other operations thatmay be performed during MUD logging will be described in further detailbelow.

The master MUD logger may send a notification to one or more MUD loggersat 510, as appropriate. The notification may indicate one or moreregions of the volume that have been modified during the epoch orindicate one or more modifications to be made to the MUD log. Moreparticularly, each of the MUD logger(s) that are exporting the volumemay be notified. Of course, it may be unnecessary to notify all of theMUD loggers. For instance, where the master has been notified of a writecommand received by another MUD logger, that MUD logger that hasnotified the master logger need not be notified of the write command. Itmay also be unnecessary to notify the other MUD logger(s) for thevolume, even where a write command addressed to particular region(s) ofthe volume has been received. For instance, where the region(s) havealready been modified during the epoch, the MUD log need not be modifiedand therefore the other MUD loggers need not be notified.

In other instances, the master MUD logger may send a notificationindicating one or more modification(s) to be made to the MUD log(e.g.,current epoch of the MUD log). Such modifications may be performed via avariety of operations on the MUD log, which will be described in furtherdetail below. For instance, where a new epoch is initiated, the masterMUD logger may send an appropriate notification. The notification mayindicate that a new epoch has started, or the notification may be morespecific, directing the other MUD logger(s) to generate a new epoch datastructure and/or clear an epoch data structure. Similarly, the masterMUD logger may send an appropriate notification to perform an operationsuch as merge two or more sequential epochs, delete, or clear an epoch.

FIGS. 6A-B are process flow diagrams illustrating methods ofimplementing MUD logging by a non-master MUD logger in accordance withone embodiment. As shown in FIG. 6A, when the non-master MUD loggerintercepts a write command at 602, the non-master MUD logger may updateits MUD log to indicate that a particular region or regions have beenmodified during the epoch at 604. This modification may be madeautomatically, or may be made only when the region(s) have not alreadybeen modified during the epoch. The non-master MUD logger may alsonotify the master MUD logger of the write command addressed to theregion(s) of the volume as shown at 606. In accordance with oneembodiment, the notification is sent during the current epoch (e.g.,upon receipt of the write command). More particularly, the non-mastermay send a notification indicating one or more modifications to be madeto the MUD log to the master MUD logger at 606, as appropriate. When themaster MUD logger receives such a notification, it modifies its own MUDlog and sends a notification, as appropriate, to other MUD loggers. Asset forth above, the notification may indicate those region(s) that havebeen modified as a result of the write command. However, where theregion(s) have already been modified during the epoch, the MUD log neednot be modified and therefore the master MUD logger need not benotified. Alternatively, a notification may identify a subset of thoseregions that have been modified during the epoch (e.g., where the subsetexcludes those regions that have not previously been modified during theepoch).

Where the non-master MUD logger does not receive a write command, it mayreceive a notification of one or more modifications to be made to theMUD log or, alternatively, modifications made to the MUD log may beinternally initiated. These modifications may be made via a variety ofoperations, which will be described in further detail below. As shown inFIG. 6B, the non-master MUD logger may receive a notification of thereceipt of a write command to one or more regions of the volume (e.g.,from the master MUD logger) as shown at 610. It is also possible thatthe non-master MUD logger may detect or receive a notification ofanother type of event from the master MUD logger (or other entity) at612. Such events may include, for example, an event indicating the startof a new epoch or a request to start a new epoch. In othercircumstances, it is possible that the non-master MUD logger mayinternally initiate a modification to its MUD log, as shown at 614. Forinstance, the non-master MUD logger may wish to consolidate itsinformation by merging two or more epochs, or delete or clear an epoch.

In any of the circumstances set forth in 610-614, the non-master MUDlogger may update its MUD log at 616, as appropriate. It is important tonote that a notification may be received (e.g., as a result of a writecommand), even where the MUD log need not be updated (e.g., if theregion(s) have already been modified during the epoch). Alternatively,the non-master MUD logger may update information for the epoch inresponse to the notification for at least one of the regions that hasbeen modified during the corresponding epoch, as appropriate. In otherwords, the information that is updated may be only for those regionsthat have not previously been modified during the current epoch.

The non-master and master MUD loggers may each make a variety ofmodifications to the MUD log that it maintains. These modifications maybe made via a variety of operations, which will be described in furtherdetail below. For instance, a MUD logger may update its MUD logassociated with the volume to indicate that the region(s) that have beenmodified (e.g., written to) during the current epoch. In this manner,information for the current epoch may be updated by logging thesegment(s) that have been modified during the current epoch.

Other operations may be performed to modify a MUD log. As one example, anew epoch may be generated. Moreover, information for one or more epochsmay be cleared or deleted. Thus, an entire MUD log may be deleted orcleared. As another example, the information for two or more epochs maybe merged, where the epochs being merged are contiguous epochs.Additional examples will be described in further detail below.

As set forth above, a MUD log includes information for one or moreepochs, where the information for each of the epochs indicates a set ofone or more regions that have been modified during the correspondingepoch. More particularly, the information for each epoch identifying theset of regions that have been modified during the corresponding epochmay include a bit map. For instance, the bit map may include a bit foreach of a plurality of regions in the volume.

In accordance with one embodiment, a bit map is maintained for thecurrent epoch, while a byte map is maintained for prior epochs. Moreparticularly, the byte map includes a byte for each region of thevolume, enabling the byte to include data for the latest epoch for whichthe region was written to.

FIGS. 7A and 7B together illustrate the application of a merge operationon a MUD log. FIG. 7A is an example diagram illustrating the informationfor two different epochs, Epoch A and Epoch B. In this example, theinformation for each epoch is implemented via a bit map. For instance,each region of the volume may correspond to a different bit in the bitmap, where each bit indicates whether the corresponding region has beenmodified during the epoch. In accordance with one embodiment, the bit isset to “1” when the region has been modified during the epoch. The bitremains set to a “0” (as initialized) when the region has not beenmodified during the epoch.

FIG. 7B is an example diagram illustrating a mechanism for merging twoor more contiguous epochs. In other words, the epochs are merged into asingle epoch spanning the time periods of the merged epochs. In order tomerge two or more epochs, an OR operation may be performed on the bitmaps for the two or more epochs. In this manner, the information for theepochs may be merged into a single bit map. In this example, Epoch A andEpoch B are merged by performing an OR operation on the bit maps,resulting in a third bit map, as shown. Epoch A and Epoch B may then bedeleted or cleared.

Other operations may also be performed during MUD logging. For instance,it may be desirable to generate a MUD log(e.g., which may include zeroor more epochs), delete a MUD log, or clear a MUD log. A MUD log may begenerated, for example, by generating a MUD log data structure viainstantiation. Each epoch may be implemented via a bit map, where thebits in the bit map are initialized to zero. A MUD log may be deleted orcleared, for example, by deleting all epochs (e.g., bit maps) in the MUDlog.

In certain circumstances, it may be desirable to generate (i.e.,initiate) a new epoch. In accordance with one embodiment, each epoch isimplemented by a data structure such as a bitmap. In order to initializethe epoch, the bits in the bitmap may be initialized to zero. A newepoch that is generated may then be made the current epoch. In othercircumstances, it may be desirable to delete one or more epochs. Forinstance, the oldest epoch(s) may be deleted in order to remove outdatedinformation. This may be accomplished by deleting the bitmap for thecorresponding epoch(s).

Logging of one or more segments to the current epoch is performed when awrite command is performed. Logging may include, for example, settingone or more bits of the current epoch bitmap to “1.” More particularly,the bit corresponding to each segment of the volume that has beenmodified is set to “1.”

Once logging has been performed, it may also be desirable to identifythe next segment that has been modified during one of the epochs. Forinstance, it may be desirable to search a bit map for bits having thevalue of “1” to identify those segments of the volume that have beenmodified during the epoch. Where the epoch was initiated upon failure ofa mirror, the data from these segments may then be used to update themirror at the end of the epoch (e.g., when the mirror is reattached).

In order to conserve memory, it may be desirable to move informationassociated with a MUD log or portion thereof to another location. Thismay be accomplished by taking a snapshot of a MUD log. Moreparticularly, taking a snapshot may involve saving a copy of the MUD logto a storage device or saving the copy in a compressed format.

In the above-described embodiments, certain modifications to MUD logsand corresponding notifications received and transmitted by the MUDloggers are described. However, it is important to note that theseexamples are merely illustrative, and therefore other modifications andcorresponding notifications are contemplated. Moreover, although theexamples set forth relate to mirroring, the disclosed embodiments may beused to maintain MUD logs for a number of epochs corresponding to avariety of events.

Various network devices may be configured or adapted for performing thedisclosed functionality. These network devices include, but are notlimited to, servers (e.g., hosts), routers, and switches. Moreover, thefunctionality for the disclosed processes may be implemented in softwareas well as hardware. In accordance with various embodiments, variousswitches within a storage area network may be virtualization switchessupporting virtualization functionality. FIG. 8A is a block diagramillustrating an example virtualization switch in which variousembodiments may be implemented. As shown, data is received by anintelligent, virtualization port via a bi-directional connector 802. Inassociation with the incoming port, Media Access Control (MAC) block 804is provided, which enables frames of various protocols such as Ethernetor fibre channel to be received. In addition, a virtualization interceptswitch 806 determines whether an address specified in an incoming framepertains to access of a virtual storage location of a virtual storageunit representing one or more physical storage locations on one or morephysical storage units of the storage area network. In this example, theframe is received via a bi-directional connector 802 and the new ormodified frame exits from the switch fabric 820. However, it isimportant to note that a virtualization switch may be implemented in analternate manner. For instance, the frame may be received from thefabric 820, redirected by 806 to 808, virtualized and sent back to theswitch fabric 820. This is important when a host and disk are connectedto a standard line card such as that illustrated in FIG. 8B, and thehost and disk share several virtualization cards such as thatillustrated in FIG. 8A.

When the virtualization intercept switch 806 determines that the addressspecified in an incoming frame pertains to access of a virtual storagelocation rather than a physical storage location, the frame is processedby a virtualization processor 808 capable of performing a mappingfunction such as that described above. More particularly, thevirtualization processor 808 obtains a virtual-physical mapping betweenthe one or more physical storage locations and the virtual storagelocation. In this manner, the virtualization processor 808 may look upeither a physical or virtual address, as appropriate. For instance, itmay be necessary to perform a mapping from a physical address to avirtual address or, alternatively, from a virtual address to one or morephysical addresses.

Once the virtual-physical mapping is obtained, the virtualizationprocessor 808 may then employ the obtained mapping to either generate anew frame or modify the existing frame, thereby enabling the frame to besent to an initiator or a target specified by the virtual-physicalmapping. For instance, a frame may be replicated multiple times in thecase of a mirrored write. This replication requirement may be specifiedby a virtual-physical mapping function. In addition, the source addressand/or destination addresses are modified as appropriate. For instance,for data from the target, the virtualization processor replaces thesource address, which was originally the physical LUN address with thecorresponding virtual LUN and virtual address.

In the destination address, the port replaces its own address with thatof the initiator. For data from the initiator, the port changes thesource address from the initiator's address to the port's own address.It also changes the destination address from the virtual LUN/address tothe corresponding physical LUN/address. The new or modified frame maythen be provided to the virtualization intercept switch 306 to enablethe frame to be sent to its intended destination.

While the virtualization processor 808 obtains and applies thevirtual-physical mapping, the frame or associated data may be stored ina temporary memory location (e.g., buffer) 810. In addition, it may benecessary or desirable to store data that is being transmitted orreceived until it has been confirmed that the desired read or writeoperation has been successfully completed. As one example, it may bedesirable to write a large amount of data to a virtual LUN, which mustbe transmitted separately in multiple frames. It may therefore bedesirable to temporarily buffer the data until confirmation of receiptof the data is received. As another example, it may be desirable to reada large amount of data from a virtual LUN, which may be receivedseparately in multiple frames. Furthermore, this data may be received inan order that is inconsistent with the order in which the data should betransmitted to the initiator of the read command. In this instance, itmay be beneficial to buffer the data prior to transmitting the data tothe initiator to enable the data to be re-ordered prior to transmission.Similarly, it may be desirable to buffer the data in the event that itis becomes necessary to verify the integrity of the data that has beensent to an initiator (or target).

The new or modified frame is then received by a forwarding engine 812,which obtains information from various fields of the frame, such assource address and destination address. The forwarding engine 812 thenaccesses a forwarding table 814 to determine whether the source addresshas access to the specified destination address. More specifically, theforwarding table 814 may include physical LUN addresses as well asvirtual LUN addresses. The forwarding engine 812 also determines theappropriate port of the switch via which to send the frame, andgenerates an appropriate routing tag for the frame.

Once the frame is appropriately formatted for transmission, the framewill be received by a buffer queuing block 816 prior to transmission.Rather than transmitting frames as they are received, it may bedesirable to temporarily store the frame in a buffer or queue 818. Forinstance, it may be desirable to temporarily store a packet based uponQuality of Service in one of a set of queues that each correspond todifferent priority levels. The frame is then transmitted via switchfabric 820 to the appropriate port. As shown, the outgoing port has itsown MAC block 822 and bi-directional connector 824 via which the framemay be transmitted.

One or more ports of the virtualization switch (e.g., those ports thatare intelligent virtualization ports) may implement the disclosed MUDlogging functionality. For instance, the virtualization processor 808 ofa port that implements virtualization functionality may also perform MUDlogging functionality such as that disclosed herein. Of course, thisexample is merely illustrative. Therefore, it is important to note thata port or network device that implements MUD logging functionality maybe separate from a port or network device that implements virtualizationfunctionality.

As described above, all switches in a storage area network need not bevirtualization switches. In other words, a switch may be a standardswitch in which none of the ports implement “intelligent,”virtualization functionality. FIG. 8B is a block diagram illustrating anexample standard switch in which various embodiments may be implemented.As shown, a standard port 826 has a MAC block 804. However, avirtualization intercept switch and virtualization processor such asthose illustrated in FIG. 8A are not implemented. A frame that isreceived at the incoming port is merely processed by the forwardingengine 812 and its associated forwarding table 814. Prior totransmission, a frame may be queued 816 in a buffer or queue 818. Framesare then forwarded via switch fabric 820 to an outgoing port. As shown,the outgoing port also has an associated MAC block 822 andbi-directional connector 824.

As described above, the disclosed embodiments may be implemented, atleast in part, by a virtualization switch. Virtualization is preferablyperformed on a per-port basis rather than per switch. Thus, eachvirtualization switch may have one or more virtualization ports that arecapable of performing virtualization functions, as well as ports thatare not capable of such virtualization functions. In one embodiment, theswitch is a hybrid, with a combination of line cards as described abovewith reference to FIG. 8A and FIG. 8B.

Although the network devices described above with reference to FIGS. 8Aand 8B are described as switches, these network devices are merelyillustrative. Thus, other network devices such as routers may beimplemented to perform functionality such as that described above.Moreover, the above-described network devices are merely illustrative,and therefore other types of network devices may be implemented toperform the disclosed MUD logging functionality.

The disclosed embodiments may also be implemented via computer programproducts including machine-readable media on which are provided programinstructions for implementing the methods and techniques describedabove, in whole or in part. Any of the methods of the disclosedembodiments may be represented, in whole or in part, as programinstructions that can be provided on such machine-readable media. Inaddition, the disclosed embodiments pertain to various combinations andarrangements of data generated and/or used as described herein.

Although illustrative embodiments and applications of the disclosedembodiments are shown and described herein, many variations andmodifications are possible which remain within the concept, scope, andspirit of the disclosed embodiments, and these variations would becomeclear to those of ordinary skill in the art after perusal of thisapplication. Moreover, the disclosed embodiments would apply regardlessof the context and system in which it is implemented. Thus, broadlyspeaking, the disclosed embodiments need not be performed using theoperations or data structures described above.

In addition, although an example switch is described, theabove-described embodiments may be implemented in a variety of networkdevices (e.g., servers) as well as in a variety of mediums. Forinstance, instructions and data for implementing the above-describedembodiments may be stored on a disk drive, a hard drive, a floppy disk,a server computer, or a remotely networked computer. Accordingly, thepresent embodiments are to be considered as illustrative and notrestrictive, and the disclosed embodiments are not to be limited to thedetails given herein, but may be modified within the scope andequivalents of the appended claims.

1. A method, comprising: updating a MUD log associated with a volume bya MUD logger; and sending a notification to one or more other MUDloggers, wherein each of the one or more other MUD loggers maintains adifferent one of one or more additional MUD logs associated with thevolume, the notification indicating one or more modifications that havebeen made to the MUD log, wherein the MUD log includes information forone or more epochs, wherein the information for each of the epochsindicates a set of one or more regions of the volume that have beenmodified during the corresponding epoch.
 2. The method as recited inclaim 1, wherein sending the notification is performed in order toensure that the one or more additional MUD logs each includes theinformation for the one or more epochs.
 3. The method as recited inclaim 1, wherein each of the one or more additional MUD logs includessecond information for the one or more epochs, wherein the secondinformation for each of the epochs indicates a set of one or moreregions of the volume that have been modified during the correspondingepoch.
 4. The method as recited in claim 3, wherein sending thenotification is performed in order to cause the one or more other MUDloggers to modify the second information to conform to the informationin the MUD log.
 5. The method as recited in claim 1, wherein thenotification indicates one or more operations that have been performedon the MUD log, wherein the operations include at least one ofgenerating a new epoch in the MUD log, deleting the information for oneor more of the epochs in the MUD log, merging two or more contiguousepochs in the MUD log, deleting the MUD log, logging one or more of theregions that have been modified during one of the epochs of the MUD log,clearing the MUD log, or creating the MUD log.
 6. The method as recitedin claim 1, wherein updating the MUD log comprises: updating the MUD logassociated with the volume to indicate that at least one of the regionshave been modified during a current epoch.
 7. The method as recited inclaim 1, wherein sending a notification comprises sending a notificationby a primary MUD logger during a current epoch, the notification being anotification of a write command addressed to at least one region of thevolume, wherein the write command was intercepted by the primary MUDlogger or made known to the primary MUD logger by one of the other MUDloggers.
 8. The method as recited in claim 1, wherein the notificationindicates one or more of the regions that have been modified during acurrent epoch.
 9. The method as recited in claim 8, wherein thenotification is sent only when the one or more regions have notpreviously been modified during the current epoch.
 10. The method asrecited in claim 1, wherein sending a notification comprises: sending anotification by a secondary MUD logger during a current epoch to aprimary MUD logger, the notification being a notification of a writecommand addressed to one or more regions of the volume, wherein thewrite command has been intercepted by the secondary MUD logger.
 11. Themethod as recited in claim 10, wherein the notification is sent onlywhen the regions have not previously been modified during the currentepoch.
 12. The method as recited in claim 1, wherein sending anotification comprises: sending a notification during a current epoch ofa write command to a region of the volume.
 13. The method as recited inclaim 1, further comprising: detecting an event initiating the start ofa new epoch or receiving a notification of an event initiating the startof a new epoch.
 14. A method, comprising: receiving a notification by aMUD logger from another MUD logger maintaining another MUD log for avolume, the notification indicating one or more modifications to be madeto a MUD log maintained by the MUD logger receiving the notification,wherein the MUD log includes information for one or more epochs, whereinthe information for each of the epochs indicates a set of one or moreregions of the volume that have been modified during the correspondingepoch; and updating by the MUD logger the MUD log associated with thevolume, wherein updating the MUD log is performed in response to thenotification.
 15. The method as recited in claim 14, wherein the MUDlogger and the another MUD logger are ports.
 16. The method as recitedin claim 14, wherein updating includes at least one of deleting the MUDlog, logging one or more of the regions that have been modified duringone of the epochs of the MUD log, obtaining a snapshot of the MUD log,clearing the MUD log, or creating the MUD log, wherein the MUD log thatis created includes zero or more epochs.
 17. The method as recited inclaim 14, wherein updating comprises: deleting or clearing theinformation for one or more of the epochs.
 18. The method as recited inclaim 14, wherein updating comprises: merging the information for two ormore of the epochs, wherein the two or more epochs are contiguousepochs.
 19. The method as recited in claim 14, where the notificationindicates one or more of the regions that have been modified during acurrent epoch, and wherein updating the MUD log includes updating theinformation for the current epoch.
 20. The method as recited in claim14, wherein updating the MUD log comprises: updating the information forone of the epochs for at least one of the regions that has been modifiedduring the corresponding epoch.
 21. The method as recited in claim 14,wherein the notification is a notification of a write command to aregion of the volume.
 22. The method as recited in claim 14, wherein thenotification is a request to start a new epoch and wherein updatingincludes generating a new epoch in the MUD log,
 23. An apparatus,comprising: a processor; and a memory, at least one of the processor orthe memory being adapted for: updating a MUD log associated with avolume; and sending a notification to one or more other MUD loggers,wherein each of the one or more other MUD loggers maintains a differentone of one or more additional MUD logs associated the volume, thenotification indicating one or more modifications that have been made tothe MUD log, wherein the MUD log includes information for one or moreepochs, wherein the information for each of the epochs indicates a setof one or more regions of the volume that have been modified during thecorresponding epoch.
 24. An apparatus, comprising: a processor; and amemory, at least one of the processor or the memory being adapted for:receiving a notification by a MUD logger from another MUD loggermaintaining another MUD log for a volume, the notification indicatingone or more modifications to be made to a MUD log maintained by the MUDlogger receiving the notification, wherein the MUD log includesinformation for one or more epochs, wherein the information for each ofthe epochs indicates a set of one or more regions of the volume thathave been modified during the corresponding epoch; and updating the MUDlog associated with the volume, wherein updating the MUD log isperformed in response to the notification.
 25. An apparatus, comprising:means for updating a first MUD log associated with a volume; and meansfor sending a notification to a second MUD logger, the notificationindicating one or more modifications to be made to a second MUD logmaintained by the second MUD logger receiving the notification, whereinthe first MUD log and the second MUD log each includes information forone or more epochs indicating regions of the volume that have beenmodified during the corresponding epoch.